Release: v1.6.0 - #586
Conversation
ea536b0 to
26bf0b3
Compare
7f5bfa7 to
aa12060
Compare
3f48e96 to
b7ec20d
Compare
b7ec20d to
ae2a0df
Compare
AmaadMartin
left a comment
There was a problem hiding this comment.
The version bump is correct. All seven version locations, the manifest and the lockfile read 1.6.0, and the three compare links match the adk, devtools and integrations components in release-please-config.json.
I compared every commit on main since adk-v1.5.0 against the three changelogs. Six omissions are correct: two refactor commits are hidden by default, and four belong to the root package, which sets skip-changelog: true. Two omissions are not correct — see the inline comment.
No workflow validates the pull request title; validation.yaml runs run-tests only. A title check stops the next occurrence.
Both PR titles used "Fix <subject>" with no colon, so the squash subjects were not conventional commits and release-please dropped them from the generated changelog: d3f250e Fix unsafe A2A peer-supplied transferToAgent metadata (#596) 7bc05f6 Fix zip-slip blacklist bypass in isDangerousZipEntryName (#621) Both are core-only security fixes landed after adk-v1.5.0, so they belong in the adk 1.6.0 Bug Fixes section. Entries are inserted in the position release-please would have emitted them.
AmaadMartin
left a comment
There was a problem hiding this comment.
Approved. 48059d5 adds the two missing entries and changes nothing else.
I verified both: the full SHAs resolve to #596 (d3f250e) and #621 (7bc05f6), the descriptions match what release-please renders for the other entries, and the alphabetical order of the Bug Fixes list still holds. Both commits touch core/src only, so core is the correct changelog. All four package versions still read 1.6.0, and main has not advanced past 2c07ad3, so the notes are complete as of now.
One note that is not your bug. run-tests (windows-latest) failed the first time on unsafe_local_code_executor_test.ts > should execute shell code and return stdout, with Test timed out in 5000ms. The code tree here is identical to the green parent commit — the only delta is two lines of Markdown — so the test is flaky on Windows. It passed on a re-run. The 5s limit is tight for a test that spawns a real PowerShell process; it is worth a longer timeout, in the same spirit as #548, #549 and #550.
|
🤖 Created releases: 🌻 |
Automated Release PR
adk: 1.6.0
1.6.0 (2026-08-05)
Features
Bug Fixes
devtools: 1.6.0
1.6.0 (2026-08-05)
Features
Bug Fixes
Dependencies
integrations: 1.6.0
1.6.0 (2026-08-05)
Miscellaneous Chores
Dependencies
main: 1.6.0
1.6.0 (2026-08-05)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.